Step 4-Additional Options
- How would you like to import incoming data? (drop-down list) - This refers to the scenario (and associated alternatives) into which the data will be imported. The user can import the data into the Current Scenario or a new child scenario. If the latter is selected, a new child scenario (and child alternatives) will be created for any data difference between the source and the active scenario. If there is no data change for a particular alternative, no child alternative will be created in that case.
- New scenario and alternatives will be automatically labeled "Created by ModelBuilder" followed by the date and time when they were created.
- How would you like to map
elements in the data source to elements in the destination? - You have two
options for mapping elements, by key field or spatially.
- Map elements by key field (drop-down list): The key field represents the field in the model and data source that contains the unique identifier for associating domain elements in your model to records in your data source. Refer to the "Key Field (Model)" topic in the next section for additional guidance on how this setting applies to ModelBuilder. ModelBuilder provides three choices for Key Field: Label, GIS-ID, or <custom>.
- If several elements
share the same GIS-IDs, then apply updates to all of them? (check box) - When
using the GIS-IDs option, ModelBuilder allows you to maintain one-to-many, and
many-to-one relationships between records in your GIS and elements in your
Model.
For example, you may have a single pipe in your GIS that you want to maintain as multiple elements in your Model because you have split that pipe into two pipes elements in the model. You may accomplish this using the native Drainage and Utilities layout tools to split the pipe with a node; the newly created pipe segment will be assigned the same GIS-IDs as the original pipe (establishing a one-to-many relationship). By using this option, when you later synchronize from the GIS into your model, any data changes to the single pipe record in your GIS can be cascaded to both pipes elements in your model (e.g. so a diameter change to a single record in the GIS would be reflected in both elements in the model).
- How would you like to
handle add/removes of elements with GIS-IDs mappings on subsequent imports? -
These options are useful for keeping your GIS and Model synchronized, while
maintaining established differences.
When you do make connectivity changes to your model, it is often beneficial to make those same changes to the GIS. However, this is not always possible; and in some cases is not desirable -- given the fact that Modeling often has highly specialized needs that may not be met by a general purpose GIS.
- Map elements spatially to
closest matching geometries (spatial join): Choosing the spatial option will
disable the ability to choose a key field and enable the ability to set a
tolerance for finding closest matching geometries. The default is 100, with the
unit based on what was selected for the connection.
When mapping fields for each table, the key field will automatically be set to the <label> field generated by ModelBuilder. If a field isn't specified as the label property, this will be used for the label of any newly created elements. Elements in the data source that don't match with any existing elements in the model will be created in the same way that an element with a key field not already in the model would be created. This is still dependent on the "Add objects to the destination that are present in source" option.
When synchronizing into the model with spatial join enabled, ModelBuilder will first look for exact matches and map them. Then searches are done on the remaining elements using the specified tolerance. If there are multiple nodes found within the tolerance, the closest one is chosen. If there are multiple polylines found, the distances between the start, mid, and end points are used to choose a match. If there are multiple polygons found, the distances between centroids are used.